Phone-first — Poppy in your pocket
The same Poppy, reachable on the channel already open in the user's hand. Text her a question, snap a photo of a flyer, leave a voice note — she answers from live PURE data and proposes any action behind the usual approval.
SMS & MMS to Poppy
A dedicated number (Twilio via pure-comms). Texts + photos become a Poppy thread.
Email to Poppy
A reply-to address (Resend) opens a thread; attachments auto-ingest.
Talk & voice notes
Speak a request or send a voice memo; STT turns it into a task (3.0).
Input channels, generation by generation
| Channel | How it works | Arrives |
|---|---|---|
| Web chat | Pure Chat.ai full-page + operator + inline | 1.0 live |
| SMS / MMS to Poppy | Text a number; photos attach (Twilio / pure-comms) | 2.0 |
| Email to Poppy | Reply-to address starts a thread; files ingest (Resend) | 2.0 |
| Mobile app / PWA | Install to home screen; camera + push | 2.0 |
| Deep links / QR | Scan or tap prefilled Poppy (pure_short_urls) | 2.0 |
| Omnipresent top-bar | Poppy on every surface, hat-aware | 3.0 |
| Voice in/out | Speak to Poppy; she replies aloud | 3.0 |
| Push & proactive | She reaches out: deadlines, new matches, drift | 3.0 |
| Messaging apps | WhatsApp / iMessage business where members already are | 3.0+ |
One sign-in, growing access
Your instinct is right: get the user to sign in to Poppy once (passkey via Supabase Auth), then every account they connect lets Poppy safely do more — without ever asking them to log in again.
Sign in once — passkey
One phishing-resistant Poppy identity (Supabase Auth). No passwords, no repeat logins. This is the key that everything hangs on.
Connect an account unlock a capability
Connect Follow Up Boss Poppy reads & routes your leads. Connect Google/Zoho calendar + email context. Connect Matterport 3D tours. Each connection is a consented, revocable scope.
Auto-ingest on connect
The moment a source is linked, Poppy auto-uploads what matters — leads, contacts, calendar, documents — so the user never re-enters data. Connect, don't copy.
Access compounds over time
More connections + a higher plan = more products, services and actions available — computed live from pure_permissions + pure_subscriptions. Poppy grows with the user.
Bring your world in
- Follow Up Boss — leads + CRM
- Google / Zoho — calendar, email, contacts
- Matterport — 3D captures
- Google Maps — geo + neighborhoods
- DocuSign / Pure Signature — signing
More power, same safety
- Every connection = explicit consent + revocable in Command Center
- Scoped tokens, least-privilege; PII via OTP grants
- Writes still gated by the approval card
- Every grant + access logged to audit_log
- RLS on auth.uid — a user only ever reaches their own world
More options to consider
Frictionless input
- Share-to-Poppy from any app (photo, link, PDF)
- Forward an email/text to Poppy to file it
- Voice memo task + summary
Be where they are
- Home-screen PWA + push
- Calendar invites with a "Ask Poppy" link
- QR on signs/flyers instant property Q&A
One thread, everywhere
- Start on text, finish on web — same context
- Per-user memory carries across channels
- Handoff to a human keeps the transcript